75-100% cpu utilization spikes with single site visitor
Sorry if this is a dup. I waited 15 minutes for my other post to show up and it hasn't yet. Bummer. In any case, this post has a little more info.
Umbraco 4.0.3
Blog4Umbraco 2.0.24
Windows Server 2008
SQL Server 2008 (separate machine)
I recently (yesterday) imported 500+ blog posts and 2000+ comments from community server. I'll have several hundred more pages to go before the site is fully stocked. I had planned to go live with the blog this week, but this perf issue is a showstopper.
When hitting a single page, I'm seeing CPU spikes from 50% to 100%. That's loading the server, and making individual pages take several seconds to load. For example, this page had a 4 second CPU spike of 100%.
Once initially loaded, it's good for several minutes (presumably whatever the cache time is)
Most of my customization has been limited to skinning/templates. I've modified some xslt, but mainly just to change styles and layout. xml caching is turned on in the config. I have 500+ entries in the urlrewriting config file to map the old community server urls to the new umbraco ones.
I'm not running the image resizer (saw in other posts that it had a memory leak), and I'm not seeing anything that makes sense in the debug trace. Memory usage is pretty consistent at around 350mb. I see no errors in the windows event log.
The server (older dual proc xeon 2.4ghz) runs my blog under community server with CPU usage typically in the < 3% range, so the machine is capable.
Not sure if this is the problem, or a red herring, but I see a bunch of these in the umbraco log table:
Error removing node from umbraco index: 'System.IO.IOException: No sub-file with id _4.f8 found at Lucene.Net.Index.CompoundFileReader.OpenInput(String id) at Lucene.Net.Index.SegmentReader.OpenNorms(Directory cfsDir) at Lucene.Net.Index.SegmentReader.Initialize(SegmentInfo si) at Lucene.Net.Index.SegmentReader.Get(Directory dir, SegmentInfo si, SegmentInfos sis, Boolean closeDir, Boolean ownDir) at Lucene.Net.Index.IndexReader.AnonymousClassWith.DoBody() at Lucene.Net.Store.Lock.With.Run() at Lucene.Net.Index.IndexReader.Open(Directory directory, Boolean closeDirectory) at Lucene.Net.Index.IndexReader.Open(String path) at umbraco.cms.businesslogic.index.Indexer.RemoveNode(Int32 Id)'
I'd like to rebuild the index, but can't tell where the files are that I'd have to delete.
Any suggestions how to debug the larger perf issue?
To rebuild the index goto /umbraco/reindex.aspx that will rebuild the index for you. See if that fixes the problem if not can you tell me if in any xslt macros you are using GetXmlDocumentById?
75-100% cpu utilization spikes with single site visitor
Sorry if this is a dup. I waited 15 minutes for my other post to show up and it hasn't yet. Bummer. In any case, this post has a little more info.
I recently (yesterday) imported 500+ blog posts and 2000+ comments from community server. I'll have several hundred more pages to go before the site is fully stocked. I had planned to go live with the blog this week, but this perf issue is a showstopper.
When hitting a single page, I'm seeing CPU spikes from 50% to 100%. That's loading the server, and making individual pages take several seconds to load. For example, this page had a 4 second CPU spike of 100%.
http://10rem.net/2010/02/22/windows-client-developer-roundup-for-2222010
Once initially loaded, it's good for several minutes (presumably whatever the cache time is)
Most of my customization has been limited to skinning/templates. I've modified some xslt, but mainly just to change styles and layout. xml caching is turned on in the config. I have 500+ entries in the urlrewriting config file to map the old community server urls to the new umbraco ones.
I'm not running the image resizer (saw in other posts that it had a memory leak), and I'm not seeing anything that makes sense in the debug trace. Memory usage is pretty consistent at around 350mb. I see no errors in the windows event log.
The server (older dual proc xeon 2.4ghz) runs my blog under community server with CPU usage typically in the < 3% range, so the machine is capable.
Not sure if this is the problem, or a red herring, but I see a bunch of these in the umbraco log table:
Error removing node from umbraco index: 'System.IO.IOException: No sub-file with id _4.f8 found at Lucene.Net.Index.CompoundFileReader.OpenInput(String id) at Lucene.Net.Index.SegmentReader.OpenNorms(Directory cfsDir) at Lucene.Net.Index.SegmentReader.Initialize(SegmentInfo si) at Lucene.Net.Index.SegmentReader.Get(Directory dir, SegmentInfo si, SegmentInfos sis, Boolean closeDir, Boolean ownDir) at Lucene.Net.Index.IndexReader.AnonymousClassWith.DoBody() at Lucene.Net.Store.Lock.With.Run() at Lucene.Net.Index.IndexReader.Open(Directory directory, Boolean closeDirectory) at Lucene.Net.Index.IndexReader.Open(String path) at umbraco.cms.businesslogic.index.Indexer.RemoveNode(Int32 Id)'
I'd like to rebuild the index, but can't tell where the files are that I'd have to delete.
Any suggestions how to debug the larger perf issue?
site: http://10rem.net
Thanks.
Pete
Pete,
To rebuild the index goto /umbraco/reindex.aspx that will rebuild the index for you. See if that fixes the problem if not can you tell me if in any xslt macros you are using GetXmlDocumentById?
Regards
Ismail
Ismail, not sure how you managed to get into this thread (the % sign made it impossible to navigate to unless you manually adjusted the url to be: http://our.umbraco.org/forum/getting-started/installing-umbraco/7426-75-100#137-cpu-utilization-spikes-with-single-site-visitor ) but please check out the second thread I started on this subject:
http://our.umbraco.org/forum/getting-started/installing-umbraco/7427-75-100-percent-cpu-utilization-spikes-with-single-site-visitor
Lots more info there. Not getting any closer (other than realizing 500+ rules in urlrewriting.config runs like crap)
Thanks
Pete
is working on a reply...
This forum is in read-only mode while we transition to the new forum.
You can continue this topic on the new forum by tapping the "Continue discussion" link below.